bundle: record and read deployment state via DMS by shreyas-goenka · Pull Request #6094 · databricks/cli

shreyas-goenka · 2026-07-29T09:33:50Z

Summary

This PR adds code to read and write state using DMS, behind DATABRICKS_BUNDLE_RECORD_DEPLOYMENT_HISTORY.

Design decisions:

The version is only created after a user approves a deployment. Not before.
CreateVersion stages one operation per planned resource, so the CLI only ever calls UpdateOperation — there is no CreateOperation call. The service creates each staged operation as PENDING at sequence_id = 0, which is the precondition the CLI uses for its first update of a resource. Needs databricks-eng/universe#2420238 (merged).
Jobs and pipelines are stamped with deployment ID and version ID.

Also adds an env var to toggle DMS, and records the API status and error code with a failure.

Testing Strategy

The whole acceptance suite runs a second time with recording on (EnvMatrix.DATABRICKS_BUNDLE_RECORD_DEPLOYMENT_HISTORY), so every bundle test exercises DMS against the local test server and asserts the same golden files either way — the nostamp helper strips the deployment stamp for that. Focused coverage of the recorded calls themselves lives under acceptance/bundle/dms.

Before private preview we will:

Run these tests on cloud on our production workspaces.
TBD: Run these tests on staging workspaces as well as part of our test infra.

What is missing?

Serialized plan does not work yet. Will be fixed in a followup PR.
Issues were reported in bugbash where applies would be state or plans would not be correctly computed. This could be because of caching in the service which we are fixing with strong reads. To be investigated later in any case.

eng-dev-ecosystem-bot · 2026-07-29T10:10:48Z

Integration test report

Commit: b4d23d2

Run: 33882675175

	Env	❌FAIL	🟨KNOWN	✅pass	🙈skip	Time
❌	aws linux	27	1	275	52	5:58
❌	aws windows	27	1	277	50	5:03
❌	azure linux	27	1	274	52	6:59
❌	azure windows	27	1	276	50	6:04
❌	gcp linux	27	1	275	52	6:08
❌	gcp windows	27	1	277	50	4:45

28 interesting tests: 27 FAIL, 1 KNOWN

	Test Name	aws linux	aws windows	azure linux	azure windows	gcp linux	gcp windows
🟨	TestAccept	🟨K	🟨K	🟨K	🟨K	🟨K	🟨K
❌	TestAccept/bundle/dms/declined-deploy	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/declined-deploy/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/depends-on	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/depends-on/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/deployment-metadata-change	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/deployment-metadata-change/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/emptied-resource	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/emptied-resource/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/existing-state	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/existing-state/DATABRICKS_BUNDLE_ENGINE=direct/DMS=	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/multiple-resources	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/multiple-resources/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/no-drift	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/no-drift/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/no-resources	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/no-resources/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/provenance	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/provenance/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/record	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/record-failure	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/record-failure/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/record/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/stale-plan	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/stale-plan/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true/READPLAN=	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/stale-plan/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true/READPLAN=1	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/successful-recreate	❌F	❌F	❌F	❌F	❌F	❌F
❌	TestAccept/bundle/dms/successful-recreate/DATABRICKS_BUNDLE_ENGINE=direct/DMS=true	❌F	❌F	❌F	❌F	❌F	❌F

shreyas-goenka · 2026-07-29T13:17:25Z

+		// of and the next deploy would create them a second time. Checked here rather
+		// than only where operations are recorded, which is after the resource has
+		// already been modified.
+		if err := opQueue.firstErr(); err != nil {


we could eventually extend this to record and return all multiple errors that happened.

shreyas-goenka · 2026-07-29T13:36:18Z

@@ -0,0 +1,4 @@
+
+=== An operation upload failure fails the deploy instead of reporting only at the end


it's hard to make a assert more here because we cannot control how many requests went through. We could harden this test by making the number of workers configurable and 1. Omitting for now.

shreyas-goenka · 2026-07-29T13:44:57Z

@@ -0,0 +1,18 @@
+Local = true
+Cloud = false


We'll rollout the service to our test env by next week at which point we can start turning these tests on on cloud as well.

shreyas-goenka · 2026-07-29T13:45:22Z

+
+# Deployment Metadata Service (DMS) recording is only supported by the direct
+# engine; it is a no-op on terraform.
+EnvMatrix.DATABRICKS_BUNDLE_ENGINE = ["direct"]


Eventually we can also make DMS part of the default test matrix - to get more coverage - this can be rolled out slowly.

shreyas-goenka · 2026-07-29T14:03:26Z

+	assert.Empty(t, f.recorded())
+}
+
+func TestOperationQueueCloseIsIdempotent(t *testing.T) {


this is not strictly necessary given we only have one close site.

github-actions · 2026-07-29T15:23:27Z

Approval status: pending

`/acceptance/bundle/` - needs approval

470 files changed
Suggested: @denik
Also eligible: @pietern, @janniklasrose, @andrewnester, @lennartkats-db, @anton-107

`/bundle/` - needs approval

26 files changed
Suggested: @denik
Also eligible: @pietern, @janniklasrose, @andrewnester, @lennartkats-db, @anton-107

`/cmd/bundle/` - needs approval

Files: cmd/bundle/generate/dashboard.go, cmd/bundle/generate/genie_space.go, cmd/bundle/utils/process.go
Suggested: @denik
Also eligible: @pietern, @janniklasrose, @andrewnester, @lennartkats-db, @anton-107

General files (require maintainer)

23 files changed
Based on git history:

@denik -- recent work in bundle/direct/, bundle/phases/, libs/testserver/

_{Any maintainer (@andrewnester, @anton-107, @denik, @pietern, @simonfaltum, @renaudhartert-db, @janniklasrose, @lennartkats-db, @rugpanov, @rclarey) can approve all areas.

See OWNERS for ownership rules.}

shreyas-goenka · 2026-08-07T01:22:00Z

+	return &apiVersionCreator{client: c}
+}
+
+func (a *apiVersionCreator) CreateVersion(ctx context.Context, deploymentID, versionID string, body createVersionRequest) (*bundledeployments.Version, error) {


will be replaced with SDK calls soon in a followup.

shreyas-goenka · 2026-08-07T01:24:35Z

+// The extra field cannot be added by embedding Deployment in a wrapper struct:
+// Deployment has its own MarshalJSON, which is promoted to the wrapper and
+// silently drops any sibling field.
+func deploymentBody(d *dmsDeployment) (map[string]any, error) {


goes away on a SDK bump

shreyas-goenka · 2026-08-07T01:35:55Z

+	r := NewRecorder(RecorderOptions{Service: f, Versions: fakeVersions{requests: &f.versions}, DeploymentID: "stored-id", StatePath: testStatePath, Metadata: Metadata{TargetName: "dev", DisplayName: testDisplayName}, VersionType: VersionTypeDeploy})
+
+	err := r.CreateVersion(t.Context())
+	assert.ErrorContains(t, err, "internal error: no deployment found for the file with object id stored-id")


this should never happen if the service is working properly, since htis indicates that the file exists but there was no deployment returned by GET deployment.

denik · 2026-08-07T08:46:24Z

+			// (sv.Value) come from the write just performed; GetResourceID reads
+			// the ID assigned by Deploy. depends_on is recorded alongside the config
+			// because it cannot be recomputed from it (see dstate.RecordedState).
+			if err := opQueue.record(ctx, resourceKey, action, b.StateDB.GetResourceID(resourceKey), sv.Value, d.DependsOn); err != nil {


Correct me if I'm wrong, this records "recreate" once, correct?

We discussed sending two requests - one for Delete and one for subsequent Create.

We also discussed moving recording hooks inside SaveState, so that we record the event ASAP. I'm considering for some resources to record state earlier and/or multiple times, by moving recording into SaveState we'll be able to handle that with DMS #5391

shreyas-goenka · 2026-08-10T16:26:22Z

+	"github.com/databricks/databricks-sdk-go/service/bundledeployments"
+)
+
+// The CLI calls the operations API directly rather than through the generated


We need to fix this. I'll investigate in a followup.

shreyas-goenka · 2026-08-11T09:39:33Z

+
+// The server expires a version's lease if it does not receive a heartbeat
+// within a 2-minute TTL; we heartbeat well inside that window.
+const defaultHeartbeatInterval = 30 * time.Second


Parts of the code here should be removed and replaced by the SDK soon.

shreyas-goenka · 2026-08-11T10:39:49Z

+	// node under the state directory, so files.Delete removes it and any later call
+	// fails with 404. CompleteVersion is idempotent, so the deferred call in Destroy
+	// is a no-op after this.
+	if err := recorder.CompleteVersion(ctx, true); err != nil {


Its a bit of a chicken and egg problem. We can improve this by first cleaning up worksapce.file_path + artifact_path. Then completing the version and then deleting state_path + root_path.

Left as a followup exercise, the current PR is already big enough in scope.

shreyas-goenka · 2026-08-11T10:50:07Z

+# unset; `deploy --plan` then creates the resources without it and the next plan reports
+# drift. Stamping at plan time would mean `bundle plan` creating the deployment record,
+# which is a design decision, so the saved-plan path is left out of the DMS run for now.
+EnvMatrixExclude.dms_no_readplan = ["DATABRICKS_BUNDLE_RECORD_DEPLOYMENT_HISTORY=true", "READPLAN=1"]


We'll fix this in a followup.

shreyas-goenka · 2026-08-11T12:20:14Z

+			// failureFields. A failure that arrives before any operation exists still
+			// goes through CreateOperation below, carrying the prior state.
+			fields = failureFields
+			body = updateOperationRequest{


By omitting state here we ensure that the latest state that was uploaded in a partial operation is retained.

…lates (databricks#6220) ## Changes `bundle init` now writes `experimental.record_deployment_history: true` into the generated `databricks.yml` when `DATABRICKS_BUNDLE_INIT_RECORD_DEPLOYMENT_HISTORY` is set. It covers every built-in template that generates a `databricks.yml`, and is off by default so template output is otherwise unchanged. ## Why Lets new projects opt into recording deployment history at creation time instead of editing the config by hand afterwards. The variable is temporary and deliberately scoped to `bundle init`: it persists the setting in the generated project rather than toggling it for the bundle being run. Note the setting is still gated off (databricks#6094), so a generated project also needs `DATABRICKS_BUNDLE_FORCE_ALLOW_RECORD_DEPLOYMENT_HISTORY` to validate until that gate is lifted. The acceptance test sets both and runs `bundle validate`, so it will fail if the two ever drift apart. ## Tests New acceptance test: all five templates with the variable on, plus the default-off and explicitly-false cases.

shreyas-goenka · 2026-08-19T10:54:01Z

+	Service bundledeployments.BundleDeploymentsInterface
+
+	// raw sends what the generated client cannot; see requester.
+	raw requester


this will go away once we get everything in the SDK

general comment: please add such comments directly to code, otherwise they will be lost.

q: What's still missing from SDK?

q: What's still missing from SDK?

A couple of that need to be propogated to the SDK from the API spec. Some are still marked as development and need to be marked as PrPr.

let's mark it as PrPr and use generated client?

Record each deploy's resource state to the deployment metadata service and read it back, making the service the source of truth for a recorded bundle: the local state file becomes a tombstone and a leftover WAL is discarded. Gated on experimental.record_deployment_history (direct engine only), and supports deploy --plan. Co-authored-by: Isaac <no-reply@databricks.com>

Co-authored-by: Isaac <no-reply@databricks.com>

…anged Co-authored-by: Isaac <no-reply@databricks.com>

…source Co-authored-by: Isaac <no-reply@databricks.com>

…, drop dedicated summary test Co-authored-by: Isaac <no-reply@databricks.com>

…op redundant operation-upload-message test Co-authored-by: Isaac <no-reply@databricks.com>

…, drop serialized-plan

…rces.get_recorded_state

… stub instead of fault.py

…pen reads the workspace client from context Co-authored-by: Isaac <no-reply@databricks.com>

…hem from DeploymentBundle The phases now reach DMS through StateDB (DmsClient, OperationBuffer, TakeOperationBuffer) rather than DeploymentBundle mirror fields. The operation drain stays before CompleteVersion. Co-authored-by: Isaac <no-reply@databricks.com>

…ffer in StateDB - add dstate.StorageBackend (WORKSPACE_FILESYSTEM/DEPLOYMENT_METADATA_SERVICE), set by Open from the state marker; the plan carries its string form so deploy --plan can reject a plan whose target switched backends - StateDB owns the recording lifecycle: RecordingError() and CompleteVersion() (idempotent via versionCompleted), with the operation-buffer drain moved into Finalize; drop the exposed OperationBuffer/TakeOperationBuffer getters and the recorder() indirection - gate DMS behavior on StorageBackend()==DEPLOYMENT_METADATA_SERVICE / ConfiguresDeploymentHistory instead of DmsClient()!=nil - consolidate plan validation in validatePlan (config-vs-plan backend match + stale-plan guard) Co-authored-by: Isaac <no-reply@databricks.com>

…ate unbind, restore v3 read - rename StampDeploymentID -> StampDeploymentIdForFirstVersion (only used for the first version's id) - inline RecordDeploymentHistoryEnv into RecordsDeploymentHistory (single predicate) - unbind: drop the config-based phase check; DeploymentBundle.Unbind opens without recording, so the state marker (not the config flag) refuses a recorded deployment - restore forward-compat read of featureStateVersion=3: this CLI still writes v2, but reads a v3 state with no features and refuses one that carries a feature Co-authored-by: Isaac <no-reply@databricks.com>

Extend declined-deploy, depends-on and deployment-metadata-change to capture the serialized 'bundle plan -o json' (now carrying storage_backend), the DMS list-resources view, and the raw recorded state. deployment-metadata-change pins state_path, which print_state.py cannot resolve, so it relies on list-resources. Co-authored-by: Isaac <no-reply@databricks.com>

…ate across the suite Extend no-resources, multiple-resources, record, successful-recreate, no-drift, stale-plan, emptied-resource and provenance to capture the serialized 'bundle plan -o json' (now carrying storage_backend), the DMS list-resources view, and the raw recorded state at each steady-state point. no-drift shows only the updated resource bumping to version 2; successful-recreate shows the recreate at version 2; provenance masks the git commit. Co-authored-by: Isaac <no-reply@databricks.com>

…-version golden - deploy.go: StorageBackend() asserts the state is open, but only the direct engine opens it, so gate the DMS deployment-create block on stateEngine.IsDirect() first. Fixes a panic ("DeploymentState must be opened first") on terraform deploys, which the direct-only dms tests did not exercise. - future_version: supported state version is now 3 (v3 is read-forward-compatible), so the too-new message reports 3. Co-authored-by: Isaac <no-reply@databricks.com>

…version on recording error - C11: StateDB holds DeploymentID/LatestVersionID (set at Open from the service); CalculatePlan stamps the plan's lineage from StateDB instead of the bundle config tree (config.History stays only for 'bundle summary'). Behavior-neutral. - unbind: Open returns a sentinel ErrUnsettingRecording; DeploymentBundle.Unbind maps it to an unbind-specific message instead of the deploy/destroy-flavored guard text. - CompleteVersion now completes as Failure when the drained buffer holds a recording error, even if the caller passed success=true, so a destroy whose uploads failed keeps its deployment record. Co-authored-by: Isaac <no-reply@databricks.com>

… the readplan option The dedicated readplan test duplicated stale-plan, which already deploys from a saved raw plan under recording. Delete it and add the standard READPLAN matrix to stale-plan so its initial deploy runs both from the saved plan and recomputed - the deploy is untraced so the variant-dependent command stays out of the golden. Recorded operations still carry the deployment_id/version_id lineage (asserted in depends-on and others). Co-authored-by: Isaac <no-reply@databricks.com>

Co-authored-by: Isaac <no-reply@databricks.com>

Extend the failure-injection tests to show how DMS records a failed or refused deploy: failed-delete/recreate/update, failed-update-permissions, operation-upload-fails-once, record-failure, version-never-created (and a WORKSPACE_FILESYSTEM plan on existing-state's first deploy). Each captures the healthy recorded state and the recorded result of the failure. Co-authored-by: Isaac <no-reply@databricks.com>

… wording - rename StartRecording -> InitializeOperationBuffer (it opens the buffer; kept separate from Open because a first deploy's id does not exist until after approval) - collapse the duplicated deployment/version fields to one public pair (DeploymentID/LatestVersionID); InitializeOperationBuffer records the first-deploy id, CompleteVersion derives the version from it - RecordingError is now a no-op unless the backend is the deployment metadata service, keeping the non-recording path cleanly separate (like RecordFailure) - stop surfacing the internal "deployment metadata service" name in user-facing errors; say "deployment history feature enabled" / "the deployment history service" - drop the "in place of nil client checks" comment and restore the original featureStateVersion wording (minimal C12 diff) Co-authored-by: Isaac <no-reply@databricks.com>

shreyas-goenka mentioned this pull request Jul 29, 2026

bundle: record and read deployment state via DMS #6074

Closed

shreyas-goenka commented Jul 29, 2026

View reviewed changes

shreyas-goenka marked this pull request as ready for review July 29, 2026 15:22

shreyas-goenka requested review from andrewnester, denik, janniklasrose and pietern July 29, 2026 16:01

pavloKozlov mentioned this pull request Aug 3, 2026

bundle/direct, libs/dms: fix DMS deploy/redeploy/destroy round-trip and record git info #6139

Closed

shreyas-goenka force-pushed the isaac/pr6052-fixes branch from f38cb18 to a49f16f Compare August 7, 2026 00:10

shreyas-goenka commented Aug 7, 2026

View reviewed changes

Comment thread cmd/bundle/summary.go Outdated

shreyas-goenka commented Aug 7, 2026

View reviewed changes

denik reviewed Aug 7, 2026

View reviewed changes

shreyas-goenka commented Aug 10, 2026

View reviewed changes

shreyas-goenka commented Aug 11, 2026

View reviewed changes

ilyakuz-db mentioned this pull request Aug 11, 2026

bundle: add env var to set record_deployment_history in built-in templates #6220

Merged

shreyas-goenka mentioned this pull request Aug 11, 2026

acceptance: pin the stale-plan hole in deployment history recording #6221

Draft

shreyas-goenka commented Aug 11, 2026

View reviewed changes

shreyas-goenka requested a review from denik August 11, 2026 12:46

shreyas-goenka commented Aug 19, 2026

View reviewed changes

shreyas-goenka force-pushed the isaac/pr6052-fixes branch 7 times, most recently from 47e54da to 766a902 Compare September 3, 2026 21:37

shreyas-goenka and others added 9 commits September 4, 2026 01:55

acceptance/dms: list-resources shows empty tombstone for no-resources

a9ce3a2

Co-authored-by: Isaac <no-reply@databricks.com>

acceptance/dms: assert declined deploy leaves recorded resources unch…

4abbea0

…anged Co-authored-by: Isaac <no-reply@databricks.com>

acceptance/dms: list-resources coverage for depends-on and emptied-re…

2a56b8b

…source Co-authored-by: Isaac <no-reply@databricks.com>

acceptance/dms: inline bundle summary into no-drift + declined-deploy…

af3ffde

…, drop dedicated summary test Co-authored-by: Isaac <no-reply@databricks.com>

libs/dms: document the three SDK gaps the raw client works around; dr…

0978bb8

…op redundant operation-upload-message test Co-authored-by: Isaac <no-reply@databricks.com>

acceptance/dms: fold serialized-plan header assertion into stale-plan…

6163285

…, drop serialized-plan

acceptance/bin: centralize recorded-state reconstruction in dms_resou…

632b8ea

…rces.get_recorded_state

acceptance/dms: record-failure uses a real bogus node type + a scoped…

1b0b45f

… stub instead of fault.py

shreyas-goenka force-pushed the isaac/pr6052-fixes branch from 766a902 to 1b0b45f Compare September 4, 2026 09:18

shreyas-goenka and others added 13 commits September 4, 2026 09:30

libs/dms: gofmt the rawClient doc comment

09f61c3

bundle: make the recorded-state marker the source of truth for DMS; O…

d42b08e

…pen reads the workspace client from context Co-authored-by: Isaac <no-reply@databricks.com>

bundle/dms: trim redundant comment on the cmdctx workspace-client bridge

5f10805

Co-authored-by: Isaac <no-reply@databricks.com>

		@@ -0,0 +1,4 @@

		=== An operation upload failure fails the deploy instead of reporting only at the end

Uh oh!

Conversation

shreyas-goenka commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Testing Strategy

What is missing?

Uh oh!

eng-dev-ecosystem-bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Integration test report

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Approval status: pending

/acceptance/bundle/ - needs approval

/bundle/ - needs approval

/cmd/bundle/ - needs approval

General files (require maintainer)

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shreyas-goenka Aug 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

shreyas-goenka commented Jul 29, 2026 •

edited

Loading

eng-dev-ecosystem-bot commented Jul 29, 2026 •

edited

Loading

github-actions Bot commented Jul 29, 2026 •

edited

Loading

`/acceptance/bundle/` - needs approval

`/bundle/` - needs approval

`/cmd/bundle/` - needs approval

shreyas-goenka Aug 11, 2026 •

edited

Loading